Documenting Software Requirements Specification: A Revisit
نویسنده
چکیده
Software Requirements Specification (SRS) is the key documentation, defining the functional and non-functional system requirements. By revisiting a number of in the literature much discussed key aspects related to SRS and extracting essential views from the author’s daily work experience, this papers stresses the importance of the SRS and examines the process, which enables the emergence of a quality SRS. Business information must be acquired, discussed, analysed and digested, which forms the inputs for the documentation of SRS. A SRS typically consists of a set of documents, including the SRS itself, which is a written description of business requirements and system features, and analysis models.
منابع مشابه
Specifying semantic information on functional requirements
Requirements engineering is a challenging process in software development projects. Requirements, in general, are documented in natural language. They often have issues related to ambiguity, completeness and consistency. How to improve the quality of requirements documentation remains a classic research topic. This research aims at improving the way of editing and documenting functional require...
متن کاملRequirements Analysis for Engineering Computation
This paper argues that the reliability of engineering computation can be significantly improved by adopting software engineering methodologies for requirements analysis and specification. The argument centers around the fact that the only way to judge the reliability of a system is by comparison to a specification of the requirements. This paper also points to methods for documenting the requir...
متن کاملArtificial Intelligence for Software Engineering : Proving Correctness of Formal Net - based Specifications ( Extended
System development consists of requirements' development and software development. By requirement development we mean documenting a synopsis, a narrative and expectations, formalization and analysis through models of the problem domain, and specification of the requirements. By software development, we mean a twofold effort, starting from requirements stated in the step above mentioned: specifi...
متن کاملTowards Model-based Acceptance Testing for Scrum
In agile processes like Scrum, strong customer involvement requires techniques to support requirements analysis and acceptance testing. Additionally, test automation is crucial, as incremental development and continuous integration need high efforts for testing. To cope with these challenges, we propose a model-based technique for documenting customer’s requirements using test models. These can...
متن کاملSupplementing Process-Oriented with Structure-Oriented Design Explanation within Formal Object Oriented Method
This paper reports the results from an action research project which studies the benefits of documenting the evolution and the rationale for the evolution of a requirements specification. Earlier research into the use of ad hoc design explanation, in which design decisions were documented using the IBIS notation (Issue Based Information System) as they were made, found both benefits and weaknes...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
برای دانلود متن کامل این مقاله و بیش از 32 میلیون مقاله دیگر ابتدا ثبت نام کنید
ثبت ناماگر عضو سایت هستید لطفا وارد حساب کاربری خود شوید
ورودعنوان ژورنال:
- Computer and Information Science
دوره 3 شماره
صفحات -
تاریخ انتشار 2010